本介紹性課程將超越混亂的 「另存為」文化 ，並將版本控制系統（VCS）定義為專門用於變更管理的工具。我們將檢視從原始、手動的檔案複製——例如像 my-term-paper-2.doc——過渡到結構化系統，將歷史視為一系列邏輯快照。
1. 拓展名陷阱
在正式的 VCS 出現之前，版本管理是一種手動且容易出錯的過程，涉及檔案重命名規則（例如附加日期或「最終版」標籤）。這不可避免地導致 檔案熵增 以及資料遺失，因為使用者必須單獨記住各檔案之間的差異。
2. 結構化快照
早期的組織方式採用了 「資料夾堆疊」方法——將專案檔案手動移入垂直層級的資料夾中，並標示為 v1.0、v2.0 及 v2.1。雖然能提供時間順序記錄，但卻缺乏 原子完整性 與 可審計性。
3. 定義解決方案
定義： Git 是一種版本控制系統（VCS），專為單一任務而設計：管理您的檔案變更。
main.py
TERMINALbash — 80x24
> Ready. Click "Run" to execute.
>
QUESTION 1
According to the lesson, what is the 'Suffix Trap'?
A specialized Git command for renaming files.
The manual process of appending 'final' or dates to filenames, leading to entropy.
A security feature in modern operating systems.
An automated way to create folder snapshots.
✅ Correct!
Correct! The Suffix Trap refers to the chaotic naming of files like 'paper-v2-final-REALLY-final.doc'.❌ Incorrect
The suffix trap refers to the manual, error-prone naming conventions used before formal VCS.QUESTION 2
How does the 'folder stack' method organize project history?
By compressing all files into a single encrypted ZIP database.
By distributing files across multiple servers globally.
By manually moving project files into a vertical hierarchy of labeled folders.
By using cryptographic hashing to track bit-level changes.
✅ Correct!
Yes. This physical bloat of v1.0, v2.0, etc., was the primitive predecessor to VCS.❌ Incorrect
The folder stack is a manual physical separation of versions into directories (v1.0, v2.0, etc.).QUESTION 3
True or False: Git was created for the single task of managing changes to your files.
True
False
✅ Correct!
Exactly. Git is purpose-built as a Version Control System for change management.❌ Incorrect
Review the definition: Git is a VCS created for the single task of managing changes to files.QUESTION 4
What is the primary problem with 'shadow history' in manual versioning?
It uses too little disk space.
The user is solely responsible for remembering differences between files.
Files are automatically deleted by the system.
It requires a high-speed internet connection.
✅ Correct!
Right. Without a tool to show 'diffs', the user must guess what changed between v1 and v2.❌ Incorrect
Shadow history lacks any mechanism to revert specific lines of code without manual comparison.QUESTION 5
Which internal object was used to illustrate manual versioning in the student example?
thesis-final.pdf
my-term-paper-2.doc
research-data.csv
index.html
✅ Correct!
Correct. This object was used to show how files get duplicated and renamed manually.❌ Incorrect
The example specifically mentioned 'my-term-paper-2.doc'.Case Study: The Dissertation Disaster
Transitioning from Manual to Git
A student is working on a 100-page dissertation. They have a folder containing: 'chapter1.doc', 'chapter1_revised.doc', 'chapter1_final.doc', and 'chapter1_FINAL_v2.doc'. They accidentally deleted a paragraph in the 'FINAL_v2' version and can't remember which previous version contained the original text.
Q
1. Identify the specific manual versioning failure occurring here.
Solution:
This is a failure of 'Atomic Integrity' and 'Auditability'. Because the history is just a 'shadow history' of disconnected files, there is no automated mechanism to compare (diff) or revert specific lines of text.
This is a failure of 'Atomic Integrity' and 'Auditability'. Because the history is just a 'shadow history' of disconnected files, there is no automated mechanism to compare (diff) or revert specific lines of text.
Q
2. How would Git's approach to 'Logical Snapshots' solve this problem?
Solution:
Instead of creating redundant files, Git would store a single 'chapter1.doc' and track the changes. The student could use Git to view the exact history of that file and restore the missing paragraph from any previous commit (snapshot) instantly.
Instead of creating redundant files, Git would store a single 'chapter1.doc' and track the changes. The student could use Git to view the exact history of that file and restore the missing paragraph from any previous commit (snapshot) instantly.
Q
3. What is the 'physical bloat' represented in the folder stack method?
Solution:
Physical bloat refers to the redundant disk space used by storing full copies of files for every minor change, whereas modern VCS often store changes (deltas) or use compression/hashing to optimize space.
Physical bloat refers to the redundant disk space used by storing full copies of files for every minor change, whereas modern VCS often store changes (deltas) or use compression/hashing to optimize space.